Problem by "NoSuchFlowException"

--0-1778151907-1269941750=:56272
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

We have 4 Jboss AS which are load-balanced via Apache Http Server with mod_=
jk 1.2.28.=20

If a request from client comes, this will be forward to one of the JBoss in=
stance assumed JB1. A session is built and began in JB1 with a session-id. =
All the requests and responses after that will be kept in this session till=
the client close it.

But sometimes the connection btw. Apache and JB1 is brocken and if a reques=
t comes the Apache send this to another JB-instance assumed JB3. Since the =
session-id is not began by JB3, therefore JB3 throws an exception in the se=
rver.log "NoSuchConversationException". One can find the session-id which b=
egan in Jb1 in Jb3 server.log.

I am not sure if our parameters in workers.properties are correct? Or shoul=
d we use additionally clustering in Jboss.

Regards

Thomas





The parameters in the workers.properties look as follow:

....
###################################
#=A0 3. Define the Template
###################################
worker.template.connection_pool_timeout=3D300
worker.template.socket_timeout=3D60
worker.template.socket_connect_timeout=3D60000
worker.template.socket_keepalive=3DTrue
worker.template.lbfactor=3D1
worker.template.type=3Dajp13
worker.template.ping_timeout=3D10000
worker.template.ping_mode=3DA
worker.template.retries=3D2
worker.template.activation=3DA
worker.template.recovery_options=3D7
....

###################################
#=A0 4.1 Set properties for worker_monther. If you have more than one worke=
r_son, just separate them with ','.
#    =A0 And you have to set the properties similar to 3.1.1.
###################################
#Load balancer for appl-icf.proactiv.de
worker.worker1.balance_workers=3Djb1,jb2,jb3,jb4
worker.worker1.sticky_session=3DTrue
worker.worker1.type=3Dlb
worker.worker1.error_escalation_time=3D0

###################################
#=A0 4.1.1 Set the properties for worker_son.
###################################
worker.jb1.reference=3Dworker.template
worker.jb1.port=3D8009
worker.jb1.host=3Dappl1-web.mycom.com
....


On the Jboss AS site the jvm parameter look as follow:

....
1.3"
  =A0 useBodyEncodingForURI=3D"true"
         emptySessionPath=3D"false" enableLookups=3D"false"=
redirectPort=3D"8443"=20
         maxThreads=3D"400"=20
         minSpareThreads=3D"25"=20
         maxSpareThreads=3D"75"=20
         acceptCount=3D"100"
  =A0 =A0connectionTimeout=3D"300000" />
....





__________________________________________________=0AD o You Yahoo!?=
=0ASie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Sc=
hutz gegen Massenmails. =0Ahttp://mail.yahoo.com
--0-1778151907-1269941750=:56272
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Browser Waiting for reply - 403 in access_log

--_f19a8c44-4cd9-4856-b5da-c27ae7e4bec7_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



Dear=2C


I am using apaci 2.2.13 with mod_ssl enabled.
When credentials are validated apaci proxy the request (ProxyPass/ProxyPass=
Reverse)

After thousands of successful requests=2C browser remains with the status "=
Web site found... Waiting for reply..."
In the mean time=2C I can see the request in access_log in apaci with 403.

[30/Mar/2010:11:27:28 +0200] "GET /RDS/portal/RDSPortal HTTP/1.1" 403 -

Any idea why 403 is generated and not sent to the browser?

Is this due to an error in proxy config?

Reloading the config allows to fix the problem (at least for thousand times=
). Is this related?

Thanks.

Regards=2C

P.

=20
____________________________________________________________ _____
Hotmail: Trusted email with powerful SPAM protection.
https://signup.live.com/signup.aspx?id=3D60969=

--_f19a8c44-4cd9-4856-b5da-c27ae7e4bec7_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable







Dear=2C


I am using apaci 2.2.13 with mod_ssl enabled.
Whe=
n credentials are validated apaci proxy the request (ProxyPass/ProxyPassRev=
erse)

After thousands of successful requests=2C browser remains with=
the status "Web site found... Waiting for reply..."
In the mean time=2C=
I can see the request in access_log in apaci with 403.

 =3B[30/=
Mar/2010:11:27:28 +0200] "GET /RDS/portal/RDSPortal HTTP/1.1" 403 -

=
Any idea why 403 is generated and not sent to the browser?

Is this d=
ue to an error in proxy config?

Reloading the config allows to fix t=
he problem (at least for thousand times). Is this related?

Thanks. r>
Regards=2C

P.